Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1600

reference
498-tree-1
name
1600
tree-preservation-order

undefined

498-tpo-1
uprn
address-text
point
POINT (-1.036817 50.886710)
geometry
MULTIPOLYGON (((-1.036746 50.886702,-1.036749 50.886716,-1.036759 50.886729,-1.036774 50.886739,-1.036794 50.886745,-1.036816 50.886748,-1.036838 50.886746,-1.036858 50.886740,-1.036874 50.886730,-1.036884 50.886717,-1.036888 50.886703,-1.036885 50.886690,-1.036875 50.886677,-1.036859 50.886667,-1.036840 50.886660,-1.036818 50.886658,-1.036796 50.886660,-1.036776 50.886666,-1.036760 50.886676,-1.036750 50.886688,-1.036746 50.886702)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL